Skip to content

Handle explicit nulls for field with default value in json deserialization #205

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
devnatan merged 5 commits into from
Dec 20, 2025
Merged

Handle explicit nulls for field with default value in json deserialization #205

devnatan merged 5 commits into from
Dec 20, 2025

Conversation

@devnatan
Copy link
Owner

@devnatan devnatan commented Dec 20, 2025 •
edited
Loading

Fixes cases when Docker returns null for a nullable API field but in Docker Kotlin field declaration it is defined as non-null (we expect a default value).

Example:

docker-kotlin/src/commonMain/kotlin/me/devnatan/dockerkt/models/container/ContainerConfig.kt

Line 27 in f8c8d54

@SerialName("Cmd") public val command: List<String> = emptyList(),

Stack-trace:

kotlinx.serialization.json.internal.JsonDecodingException:
Unexpected JSON token at offset 5874: Expected start of the array '[', but had 'n' instead at path: $.Config.Cmd

@devnatan devnatan self-assigned this Dec 20, 2025
@devnatan devnatan changed the title Do not require explicit nulls in json deserialization Handle explicit nulls for field with default value in json deserialization Dec 20, 2025
@devnatan devnatan merged commit 789fb85 into main Dec 20, 2025
1 of 2 checks passed
@devnatan devnatan deleted the fix/null-cmd-containerconfig branch December 20, 2025 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@devnatan devnatan

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@devnatan